System and method of secure message processing

ABSTRACT

A system and method for handling message indicator processing on a wireless mobile communications device. Message state data is stored in a cache for use in generating message indicators.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to and the benefit of U.S. provisionalapplication Ser. No. 60/494,621 (entitled “System and Method ofEfficient Secure Email Icon Processing” filed Aug. 12, 2003). By thisreference, the full disclosure, including the drawings, of U.S.provisional application Ser. No. 60/494,621, is incorporated herein byreference.

BACKGROUND

1. Technical Field

This invention relates generally to the field of secure electronicmessaging, and in particular to icon or other indicator processing on amessaging client on a mobile communication device.

2. Description of Related Art

Known secure messaging software clients, such as electronic mail(e-mail) software applications operating on desktop computer systems,represent the status of a secure message using a series of visualmessage indicators. These indicators include icon images, text strings,and/or a combination of both images and text.

When a secure e-mail message is displayed to the user, the state of themessage is indicated to the user as a set of message indicators. Forexample, if the content of a message is covered by a digital signature,an indicator representing that the message is signed could appear at thetop of the message body. As another example, if the content of themessage is protected by an encryption mechanism, an indicator indicatingthat the message is encrypted could appear at the top of the messagebody.

Other examples of indicators used to convey information about the stateof the message include but are not limited to: indicators representingthe trust status or revocation status of the digital certificate whosecorresponding private key is used to sign a digitally signed message;indicators representing the state of any digital certificates that areattached to the message; and indicators representing whether the senderof the message asked that a signed receipt be sent when the message isread by the recipient.

In one implementation of secure email processing, determining anddisplaying the image, text, and any other information applicable toindicator, requires considerable processing time. Many of the secureemail encoding methods in current use are complicated. Furthermore,extraction of the required information from a particular encoded messagein order to determine and to construct an applicable indicator can betime-consuming.

SUMMARY

In accordance with the teachings disclosed herein, systems and methodsare provided for handling message indicator processing on a wirelessmobile communications device. Message state data is stored in a cachefor use in generating visual message indicators.

As an example, a method may include handling an encoded message that wasreceived by a wireless mobile communications device, wherein state dataabout the encoded message is generated based upon a first access of theencoded message. The message state data is stored in a cache of themobile device and accessed based upon a second access (e.g., an opening,displaying, etc.) of the encoded message. A message indicator isgenerated based upon the message state data that was accessed from thecache and is provided to the user.

As another example, a system may include handling an encoded messagethat was received by a wireless mobile communications device. A messageprocessor on the mobile device stores the message state data in a cache.An accessing module that, based upon a second opening of the encodedmessage, retrieves from the cache the stored message state data. Amessage indicator is generated based upon the message state data that isaccessed from the cache. The generated message indicator is provided toa user of the mobile device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an overview of an example communication system in which amobile device may be used.

FIG. 2 is a block diagram depicting components used in processingmessage indicators.

FIG. 3 is a flow diagram illustrating a decision path scenario forprocessing message indicators.

FIG. 4 is a block diagram depicting updates to message state data foruse in processing message indicators.

FIG. 5 is a block diagram of a wireless mobile communication device asan example of an electronic device.

FIGS. 6-8 depict examples of indicting encryption strength.

Same reference numerals are used in different figures to denote similarelements.

DETAILED DESCRIPTION OF THE DRAWINGS

Approaches disclosed herein for providing message indicators on mobiledevices may be used with many different types of communication systems.As an example, FIG. 1 is an overview of an example communication systemin which a mobile device may be used with the approaches disclosedherein. One skilled in the art will appreciate that there may behundreds of different topologies, but the system shown in FIG. 1 helpsdemonstrate the operation of the encoded message processing systems andmethods described herein. There may also be many message senders andrecipients. The system shown in FIG. 1 is for illustrative purposesonly.

FIG. 1 shows an e-mail sender 112, the Internet 110, a message serversystem 116, a wireless gateway 106, wireless infrastructure 104 awireless network 102 and a mobile device 100. An e-mail sender system112 may, for example, be connected to an ISP (Internet Service Provider)on which a user of the system 112 has an account, located within acompany, possibly connected to a local area network (LAN), and connectedto the Internet 110, or connected to the Internet 110 through a largeASP (application service provider) such as America Online (AOL). Thoseskilled in the art will appreciate that the systems shown in FIG. 1 mayinstead be connected to a wide area network (WAN) other than theInternet, although e-mail transfers are commonly accomplished throughInternet-connected arrangements as shown in FIG. 1.

The message server 116 may be implemented on a network computer withinthe firewall of a corporation, a computer within an ISP or ASP system orthe like, and acts as the main interface for e-mail exchange over theInternet 110. Although other messaging systems might not require amessage server system 116, a mobile device 100 configured for receivingand possibly sending e-mail will typically be associated with an accounton a message server. Two common message servers are Microsoft Exchange™and Lotus Domino™. These products are often used in conjunction withInternet mail routers that route and deliver mail. These intermediatecomponents are not shown in FIG. 1, as they do not directly play a rolein the encoded message processing described below. Message servers suchas server 116 typically extend beyond just e-mail sending and receiving;they also include dynamic database storage engines that have predefineddatabase formats for data like calendars, to-do lists, task lists,e-mail and documentation.

The wireless gateway 106 and infrastructure 104 provide a link betweenthe Internet 110 and wireless network 102. The wireless infrastructure104 may determine the most likely network for locating a given user andtrack users as they roam between countries or networks. A message isthen delivered to the mobile device 100 via wireless transmission,typically at a radio frequency (RF), from a base station in the wirelessnetwork 102 to the mobile device 100. The particular network 102 may bevirtually any wireless network over which messages may be exchanged witha mobile device.

As shown in FIG. 1, a composed e-mail message 108 is sent by the e-mailsender 10, located somewhere on the Internet 110. This message 108 maybe fully in the clear and may use traditional Simple Mail TransferProtocol (SMTP), RFC822 headers and Multipurpose Internet Mail Extension(MIME) body parts to define the format of the mail message. Thesetechniques are all well known to those skilled in the art. The message108 arrives to the message server 116 and is normally stored in amessage store. Most known messaging systems support a so-called “pull”message access scheme, wherein a mobile device 100 requests that storedmessages be forwarded by the message server 116 to the mobile device100. Some systems provide for automatic routing of such messages areaddressed using a specific e-mail address associated with the mobiledevice 100. Messages may be addressed to a message server accountassociated with a host system such as a home computer or officecomputer, which belongs to the user of a mobile device 100 andredirected from the message server 116 to the mobile device 100 as theyare received.

Regardless of the specific mechanism controlling the forwarding ofmessages to a mobile device 100, the message 108, or possibly atranslated or reformatted version thereof, is sent to the wirelessgateway 106. The wireless infrastructure 104 includes a series ofconnections to wireless network 102.

FIG. 2 shows at 200 components used in processing message indicators 202on a mobile device. When a particular message 204 is opened in thisexample for the first time, the mobile device's cache 206 contains noinformation related to the message 204. The message encoding is decodedand processed at module 208 in order to determine the information 212that is to be displayed on the user interface 210 via the messageindicator(s) 202. The information 212 determined by module 208 is thensaved in the message state cache 206. Examples of such information 212include but are not limited to: the validity of the digital signaturecovering a signed message; the name and/or email address of the senderof the message; and the content cipher that was used to encrypt themessage.

The next time the message 204 is opened, the message state information212 is retrieved from the message state cache 206. This stateinformation 212 can be used to determine a number of appropriate messageindicators 202 for the message 204, and these message indicators 202 maybe displayed substantially immediately, before any message encodingprocessing takes place, such as decryption of the message. For example,the message 204 may be pre-processed before more intensive processingoccurs. The information obtained during message pre-processing (e.g.,signature status and/or trust status) can be used to populate the cacheand to generate indicator(s) for display before additional messageprocessing is performed. Other information may be available due tomessage pre-processing depending upon how the message 204 was encoded.For instance, if the message was encrypted and signed, then suchinformation as who encrypted the message, which keys were used toperform the encryption, what cipher algorithm, and the like, may be usedto generate indicator(s) before more intensive processing is performed.

Preferably, other information about the message 204, such as the decodedmessage body, could also be cached so that the entire message can bedisplayed quickly to the user. However, even without a message bodycache, the message state cache 206 can be used to render the messageindicators 202 quickly and efficiently.

It should be understood that an access of a message 204 may occur underdifferent situations. For example, the message 204 may be accessedbecause of a user-initiated action (e.g., opening the message 204) ormay be accessed automatically by the mobile device upon receipt of themessage 204. The message state data 212 stored in the cache 206 is madeavailable for subsequent accessing of the message 204. This includes themessage state data 212 being available between a first and secondopenings of the message 204, wherein the message 204 was closed by theuser between the first and second openings.

FIG. 3 is a flow diagram illustrating a decision path to process messageindicators. The process starts at the secure e-mail client application300 with the user opening a secure e-mail message at step 302. Thesystem then determines whether the message state cache containsinformation pertaining to the message at step 304. If the message statecache contains no information for the message, the system displays atemporary message indicator at step 306. The system then performs fullprocessing on the received message at step 308, and then updates thedisplay indicators at step 310.

With reference back to step 304, if the message state cache containsinformation for the message, then the system would use the message stateinformation at step 314 and determine the correct message indicator atstep 316 based on this information. The system then displays thepredetermined message indicator at step 318 and performs full processingon the received message at step 320. The indicator display may beperformed such that any visible changes in the state of the indicator beseamless to the user, thereby avoiding any visual confusion as theindicators are updated. For example, to avoid potentially confusing theuser, the mobile device's display interface is not repainted, and/or thecursor is not repositioned if it is determined that the message statehas not changed. If there is a change, then the user may be alertedaccordingly if desired.

The system then determines whether the display indicators requirefurther updating at step 322. If so, the system will update the displayindicator at step 310. If the display indicators do not need updating,the indicator will be displayed and the process is complete as shown at324.

Once the update of the display indicator (via input from steps 308and/or 310) is completed at step 310, the system will store the newmessage state information in the message state cache at step 312. Atthis point, the process is also completed as shown at 324. Other userindicators may be used if needed, such as audio indicators, icon images,text strings, and/or a combination of both images and text, if sodesired. Such indicators would be generated based upon the cachedmessage state data.

The indicators can convey many different types of message stateinformation. For example, if the content of a message is covered by adigital signature, an indicator representing that the message is signedcould appear at the top of the message body. As another example, if thecontent of the message is protected by an encryption mechanism, anindicator indicating that the message is encrypted could appear at thetop of the message body.

Other examples of indicators used to convey information about the stateof the message include but are not limited to: indicators representingthe trust status or revocation status of the digital certificate whosecorresponding private key is used to sign a digitally signed message;indicators representing the state of any digital certificates that areattached to the message; and indicators representing whether the senderof the message asked that a signed receipt be sent when the message isread by the recipient. The operational scenario of the flow chartillustrates that the user experiences minimum delay before an indicatoris displayed due at least in part to being less processor-intensive.

With reference to FIG. 4, after the message indicators 202 have beenrendered using the cached message state data 212, an application maycontinue to process the encoded message 204. The continued processingcan be done by a background thread 400 which is invisible/unnoticeableto the user. This is done in case any of the cached message state hasbeen rendered invalid by changes in the operating environment since themessage 204 was last opened and the message state data was cached. Someexamples of changes in the operating environment that may trigger anindicator change include the revocation of the digital certificate whosecorresponding private key is used to sign a changed message, theaddition of a related digital certificate to a set of trustedcertificates in the system, change in validity of the certificate, ortampering of the message or signature.

If any such indicator changes have occurred, the application wouldupdate the message indicators 202 from the background thread 400 toreflect the new values. The updated message state information 402 wouldthen be cached again, overwriting the existing cached data. If any suchchanges had not occurred, the message indicators 202 would not beupdated. Consequently, the user is only made visually aware of anybackground message processing when the state of the displayed messageindicators 202 is incorrect.

The cache 206 can be cleared of any sensitive information about themessage 204 when one of a set of events occurs. For example, if the userselects a particular menu item, or if the system goes into a lockedmode, or a mode where the device is locked up and no activity can beperformed, any sensitive data can be removed from the cache 206.

In the system shown in FIG. 4, software instructions, (e.g., implementedas an accessing and indication generation module 404) allow for themessage state information, including any message state updates 402, tobe retrieved over multiple message openings from the cache 206 for usein generating indicator(s) 202. Accordingly, the message state data 212that was stored in the cache 206 due to a first opening of the encodedmessage 204 is made available for retrieval from the cache 206 for asecond opening of the encoded message 204 and other subsequent messageaccesses and openings.

The above-described systems and methods of the present invention areintended to be examples only. Those of skill in the art may effectalterations, modifications and variations to the particular embodimentswithout departing from the scope of the invention which is defined bythe claims. For example, data signals transmitted using a communicationchannel may be used with the systems and methods. The data signals caninclude any type of data or voice information, such as an encodedmessage provided to a mobile device. The data signal may be packetizeddata that is transmitted through a carrier wave across the network.Still further computer-readable media may be used that is capable ofcausing a mobile device to perform the methods disclosed herein.

As another example, the systems and methods disclosed herein may be usedwith many different types of electronic devices. FIG. 5 is a blockdiagram of a wireless mobile communication device as an example of suchan electronic device. The mobile device 500 is preferably a two-waycommunication device having at least voice and data communicationcapabilities. The mobile device 500 preferably has the capability tocommunicate with other computer systems on the Internet. Depending onthe functionality provided by the mobile device, the mobile device maybe referred to as a data messaging device, a two-way pager, a cellulartelephone with data messaging capabilities, a wireless Internetappliance, or a data communication device (with or without telephonycapabilities). As mentioned above, such devices are referred togenerally herein simply as mobile devices.

The mobile device 500 includes a transceiver 511, a microprocessor 538,a display 522, non-volatile memory 524, random access memory (RAM) 526,auxiliary input/output (I/O) devices 528, a serial port 530, a keyboard532, a speaker 534, a microphone 536, a short-range wirelesscommunications sub-system 540, and may also include other devicesub-systems 542. The transceiver 511 preferably includes transmit andreceive antennas 516, 518, a receiver (Rx) 512, a transmitter (Tx) 514,one or more local oscillators (LOs) 513, and a digital signal processor(DSP) 520. Within the non-volatile memory 524, the mobile device 500includes a plurality of software modules 524A-524N that can be executedby the microprocessor 538 (and/or the DSP 520), including a voicecommunication module 524A, a data communication module 524B, and aplurality of other operational modules 524N for carrying out a pluralityof other functions.

The mobile device 500 is preferably a two-way communication devicehaving voice and data communication capabilities. Thus, for example, themobile device 500 may communicate over a voice network, such as any ofthe analog or digital cellular networks, and may also communicate over adata network. The voice and data networks are depicted in FIG. 5 by thecommunication tower 519. These voice and data networks may be separatecommunication networks using separate infrastructure, such as basestations, network controllers, etc., or they may be integrated into asingle wireless network. References to the network 519 should thereforebe interpreted as encompassing both a single voice and data network andseparate networks.

The communication subsystem 511 is used to communicate with the network519. The DSP 520 is used to send and receive communication signals toand from the transmitter 514 and receiver 512, and also exchange controlinformation with the transmitter 514 and receiver 512. If the voice anddata communications occur at a single frequency, or closely-spaced setof frequencies, then a single LO 513 may be used in conjunction with thetransmitter 514 and receiver 512. Alternatively, if differentfrequencies are utilized for voice communications versus datacommunications or the mobile device 500 is enabled for communications onmore than one network 519, then a plurality of LOs 513 can be used togenerate frequencies corresponding to those used in the network 519.Although two antennas 516, 518 are depicted in FIG. 5, the mobile device500 could be used with a single antenna structure. Information, whichincludes both voice and data information, is communicated to and fromthe communication module 511 via a link between the DSP 520 and themicroprocessor 538.

The detailed design of the communication subsystem 511, such asfrequency band, component selection, power level, etc., is dependentupon the communication network 519 in which the mobile device 500 isintended to operate. For example, a mobile device 500 intended tooperate in a North American market may include a communication subsystem511 designed to operate with the Mobitex or DataTAC mobile datacommunication networks and also designed to operate with any of avariety of voice communication networks, such as AMPS, TDMA, CDMA, PCS,etc., whereas a mobile device 500 intended for use in Europe may beconfigured to operate with the GPRS data communication network and theGSM voice communication network. Other types of data and voice networks,both separate and integrated, may also be utilized with the mobiledevice 500.

Communication network access requirements for the mobile device 500 alsovary depending upon the type of network 519. For example, in the Mobitexand DataTAC data networks, mobile devices are registered on the networkusing a unique identification number associated with each device. InGPRS data networks, however, network access is associated with asubscriber or user of the mobile device 500. A GPRS device typicallyrequires a subscriber identity module (“SIM”), which is required inorder to operate the mobile device 500 on a GPRS network. Local ornon-network communication functions (if any) may be operable, withoutthe SIN, but the mobile device 500 is unable to carry out functionsinvolving communications over the network 519, other than any legallyrequired operations, such as ‘911’ emergency calling.

After any required network registration or activation procedures havebeen completed, the mobile device 500 is able to send and receivecommunication signals, preferably including both voice and data signals,over the network 519. Signals received by the antenna 516 from thecommunication network 519 are routed to the receiver 512, which providesfor signal amplification, frequency down conversion, filtering, channelselection, etc., and may also provide analog to digital conversion.Analog to digital conversion of the received signal allows more complexcommunication functions, such as digital demodulation and decoding, tobe performed using the DSP 520. In a similar manner, signals to betransmitted to the network 519 are processed, including modulation andencoding, for example, by the DSP 520 and are then provided to thetransmitter 514 for digital to analog conversion, frequency upconversion, filtering, amplification and transmission to thecommunication network 519 via the antenna 518. Although a singletransceiver 511 is shown for both voice and data communications, inalternative embodiments, the mobile device 500 may include multipledistinct transceivers, such as a first transceiver for transmitting andreceiving voice signals, and a second transceiver for transmitting andreceiving data signals, or a first transceiver configured to operatewithin a first frequency band, and a second transceiver configured tooperate within a second frequency band.

In addition to processing the communication signals, the DSP 520 alsoprovides for receiver and transmitter control. For example, the gainlevels applied to communication signals in the receiver 512 andtransmitter 514 may be adaptively controlled through automatic gaincontrol algorithms implemented in the DSP 520. Other transceiver controlalgorithms could also be implemented in the DSP 520 in order to providemore sophisticated control of the transceiver 511.

The microprocessor 538 preferably manages and controls the overalloperation of the mobile device 500. Many types of microprocessors ormicrocontrollers could be used here, or, alternatively, a single DSP 520could be used to carry out the functions of the microprocessor 538.Low-level communication functions, including at least data and voicecommunications, are performed through the DSP 520 in the transceiver511. High-level communication applications, including the voicecommunication application 524A, and the data communication application524B are stored in the non-volatile memory 524 for execution by themicroprocessor 538. For example, the voice communication module 524A mayprovide a high-level user interface operable to transmit and receivevoice calls between the mobile device 500 and a plurality of other voicedevices via the network 519. Similarly, the data communication module524B may provide a high-level user interface operable for sending andreceiving data, such as e-mail messages, files, organizer information,short text messages, etc., between the mobile device 500 and a pluralityof other data devices via the network 519.

The microprocessor 538 also interacts with other device subsystems, suchas the display 522, RAM 526, auxiliary I/O devices 528, serial port 530,keyboard 532, speaker 534, microphone 536, a short-range communicationssubsystem 540 and any other device subsystems generally designated as542. For example, the modules 524A-N are executed by the microprocessor538 and may provide a high-level interface between a user of the mobiledevice and the mobile device. This interface typically includes agraphical component provided through the display 522, and aninput/output component provided through the auxiliary I/O devices 528,keyboard 532, speaker 534, or microphone 536.

Some of the subsystems shown in FIG. 5 perform communication-relatedfunctions, whereas other subsystems may provide “resident” or on-devicefunctions. Notably, some subsystems, such as keyboard 532 and display522 may be used for both communication-related functions, such asentering a text message for transmission over a data communicationnetwork, and device-resident functions such as a calculator or task listor other PDA type functions.

Operating system software used by the microprocessor 538 is preferablystored in a persistent store such as the non-volatile memory 524. Inaddition to the operating system and communication modules 524A-N, thenon-volatile memory 524 may include a file system for storing data. Thenon-volatile memory 524 may also include data stores for ownerinformation and owner control information. The operating system,specific device applications or modules, or parts thereof, may betemporarily loaded into a volatile store, such as RAM 526 for fasteroperation. Moreover, received communication signals may also betemporarily stored to RAM 526, before permanently writing them to a filesystem located in the non-volatile memory 524. The non-volatile memory524 may be implemented, for example, with Flash memory, non-volatileRAM, or battery backed-up RAM.

An exemplary application module 524N that may be loaded onto the mobiledevice 500 is a PIM application providing PDA functionality, such ascalendar events, appointments, and task items. This module 524N may alsointeract with the voice communication module 524A for managing phonecalls, voice mails, etc., and may also interact with the datacommunication module 524B for managing e-mail communications and otherdata transmissions. Alternatively, all of the functionality of the voicecommunication module 524A and the data communication module 524B may beintegrated into the PIM module.

The non-volatile memory 524 preferably provides a file system tofacilitate storage of PIM data items on the device. The PIM applicationpreferably includes the ability to send and receive data items, eitherby itself, or in conjunction with the voice and data communicationmodules 524A, 524B, via the wireless network 519. The PIM data items arepreferably seamlessly integrated, synchronized and updated, via thewireless network 519, with a corresponding set of data items stored orassociated with a host computer system, thereby creating a mirroredsystem for data items associated with a particular user.

The mobile device 500 is manually synchronized with a host system byplacing the mobile device 500 in an interface cradle, which couples theserial port 530 of the mobile device 500 to a serial port of the hostsystem. The serial port 530 may also be used to insert owner informationand owner control information onto the mobile device 500 and to downloadother application modules 524N for installation on the mobile device500. This wired download path may further be used to load an encryptionkey onto the mobile device 500 for use in secure communications, whichis a more secure method than exchanging encryption information via thewireless network 519.

Owner information, owner control information and additional applicationmodules 524N may be loaded onto the mobile device 500 through thenetwork 519, through an auxiliary I/O subsystem 528, through theshort-range communications subsystem 540, or through any other suitablesubsystem 542, and installed by a user in the non-volatile memory 524 orRAM 526. Such flexibility in application installation increases thefunctionality of the mobile device 500 and may provide enhancedon-device functions, communication-related functions, or both. Forexample, secure communication applications may enable electroniccommerce functions and other such financial transactions to be performedusing the mobile device 500.

When the mobile device 500 is operating in a data communication mode, areceived signal, such as a text message or a web page download, will beprocessed by the transceiver 511 and provided to the microprocessor 538,which preferably further processes the received signal for output to thedisplay 522, or, alternatively, to an auxiliary I/O device 528. Ownerinformation, owner control information, commands or requests related toowner information or owner control information, and softwareapplications received by the transceiver 511 are processed as describedabove. A user of mobile device 500 may also compose data items, such asemail messages, using the keyboard 532, which is preferably a completealphanumeric keyboard laid out in the QWERTY style, although otherstyles of complete alphanumeric keyboards such as the known DVORAK stylemay also be used. User input to the mobile device 500 is furtherenhanced with the plurality of auxiliary I/O devices 528, which mayinclude a thumbwheel input device, a touchpad, a variety of switches, arocker input switch, etc. The composed data items input by the user arethen transmitted over the communication network 519 via the transceiver511.

When the mobile device 500 is operating in a voice communication mode,the overall operation of the mobile device 500 is substantially similarto the data mode, except that received signals are output to the speaker534 and voice signals for transmission are generated by a microphone536. In addition, the secure messaging techniques described above mightnot necessarily be applied to voice communications. Alternative voice oraudio I/O devices, such as a voice message recording subsystem, may alsobe implemented on the mobile device 500. Although voice or audio signaloutput is accomplished through the speaker 534, the display 522 may alsobe used to provide an indication of the identity of a calling party, theduration of a voice call, or other voice call related information. Forexample, the microprocessor 538, in conjunction with the voicecommunication module 524A and the operating system software, may detectthe caller identification information of an incoming voice call anddisplay it on the display 522.

A short-range communications subsystem 540 is also be included in themobile device 500. For example, the subsystem 540 may include aninfrared device and associated circuits and components, or a Bluetoothor 802.11 short-range wireless communication module to provide forcommunication with similarly-enabled systems and devices. Thus, ownerinformation insertion, owner control information insertion, andapplication loading operations as described above may be enabled on themobile device 500 via the serial port 530 or other short-rangecommunications subsystem 540.

FIG. 5 represents a specific example of an electronic device in whichowner control systems and methods described above may be implemented.Implementation of such systems and methods in other electronic deviceshaving further, fewer, or different components than those shown in FIG.5 may be used.

As another example of the wide scope of the systems and methodsdisclosed herein and the many different types of message state data thatcan be generated and stored in cache 206, FIG. 6 illustrates thegeneration of security reliability (e.g., trust) level indicators on amobile device 610. In the example of FIG. 6, an electronic message 600(e.g., e-mail) is sent to the mobile device 610 by use of wirelessnetwork 612. Electronic message 600 may be secured by a variety ofmethods and transmitted along with associated security-relatedinformation such as a digital signature or certificate chain. It ispossible for security-related information associated with electronicmessage 600 to be sent separately from the electronic message 600.

When the mobile device 610 receives an electronic e-mail message and itsassociated security-related information 600, the mobile device 610proceeds to decrypt the message 600 and verify the identity of thesender using known techniques. The mobile device 610 determines thetrust or reliability strength of the cipher used by referring to apolicy store 604 on the mobile device 610. Policy store 604 containsrelevant details of available ciphers and their respective securitytrust classifications. On the mobile device 610, a comparator module 602can be invoked to perform a comparison between the message'ssecurity-related information and the information stored in the policystore 604. Based upon the comparison, a corresponding security trustlevel or category is determined for the message and stored in cache 206.As disclosed above, an indicator 606 of the corresponding security trustlevel is provided to the device's user interface 608.

As an example, if the cipher used to encrypt the message 600 isclassified in the policy store 604 as a “weak” cipher, then the user ispresented with an indication 606 that the cipher is classified as“weak.” As different users or organizations may have different standardsused to determine the security trust provided by ciphers, the policystore 604 allows an information technology (IT) administrator to storeclassifications for known ciphers based on relevant standards. Theseclassifications can typically be referred to as cipher policies. Forinstance, the IT administrator for a government agency may prescribemore stringent tests for a cipher, while the IT administrator for acorporate agency may prescribe less stringent tests. This may lead to acipher being classified as “weak” by the government agency, but as“strong” by the corporate agency. These cipher policies may be deployed“over the air” to the mobile device 610 through the wireless network612, thereby allowing the mobile device 610 to always maintain anup-to-date set of cipher policies. Cipher polices deployed through thewireless network 612 by the IT administrator, may be used to update thepolicy store 604 of the device 610.

In this example, ciphers are classified as being either “weak” or“strong”. Any number of alternate classifications may also be used asneeded. FIG. 7 shows an example screen of the mobile device 610. In thiscase, the message 700 was encrypted using a “strong” cipher. A lock icon710 indicates that the message 700 was encrypted, while an encryptionindication message 712 indicates the secure messaging protocol (S/MIME)and the cipher (Triple-DES) were used. As an illustration, theencryption indication message 712 could be “Encrypted using S/MIME usingTriple-DES cipher” or any other similar message. As shown in FIG. 7,message 712 can be configured to indicate to the user that a strongcipher was used.

As another example, FIG. 8 shows a screen demonstrating a sample message700 shown to the user in the case that the cipher used to encrypt themessage 700 was classified as weak. In the example, the lock icon 710indicates to the user, that the message 700 was an encrypted message,while the question mark 802 may indicate that a “weak” cipher was used.Additionally, the encryption indication message 800 could be “Weaklyencrypted using S/MIME using Triple-DES DES cipher” or a similarmessage. In both example cases, the user may select the lock icon 710 torequest details of the secure message protocol and the cipher used.Alternatively, the user may request additional details from a menuprovided to the user. As a result, the user may know whether the message700 was encrypted using a “strong” or a “weak” cipher or some othercategory of ciphers based on a cipher policy determined by theiradministrator.

1. A method for handling an encoded message that was received by awireless mobile communications device, wherein state data about theencoded message is generated based upon a first access of the encodedmessage, comprising the steps of: storing the generated message statedata in a cache of the mobile device; accessing from the cache thestored message state data based upon a second access of the encodedmessage; generating a message indicator based upon the message statedata that was accessed from the cache; wherein the generated messageindicator is provided to a user of the mobile device.
 2. The method ofclaim 1, wherein the generated message indicator includes an icon, text,graphic, or audio that is presented to the user of the mobile device. 3.The method of claim 1, wherein the generated message indicatorrepresents that the received encoded message was signed.
 4. The methodof claim 1, wherein the generated message indicator represents that thereceived encoded message was protected by an encryption mechanism. 5.The method of claim 1, wherein the generated message indicatorrepresents trust status or revocation status of the encoded message'sdigital certificate.
 6. The method of claim 1, wherein the generatedmessage indicator represents validity status of a digital certificatethat is attached to the encoded message.
 7. The method of claim 1,wherein the generated message indicator represents whether the sender ofthe encoded message asked that a signed receipt be sent when the encodedmessage is read by the recipient.
 8. The method of claim 1, wherein themessage state data is stored in the cache after the content in theencoded message was accessed for the first time, wherein the messagestate data is stored for subsequent openings of the content in theencoded message.
 9. The method of claim 8, wherein before the accessingof the encoded message for the first time the cache does not containmessage state data related to the encoded message.
 10. The method ofclaim 9, wherein the stored message state data includes validity of thedigital signature associated with the encoded message.
 11. The method ofclaim 9, wherein the stored message state data includes message senderinformation.
 12. The method of claim 9, wherein the message state dataincludes information about a content cipher that was used to encrypt theencoded message.
 13. The method of claim 1, wherein the generatedmessage indicator is displayed substantially immediately, before anymessage encoding processing occurs with respect to the encoded message.14. The method of claim 1, wherein decoded message body of the encodedmessage is also stored in cache for use in subsequent openings involvingthe received encoded message.
 15. The method of claim 1, furthercomprising the steps of: determining whether the cache contains messagestate data about the received encoded message; wherein if the messagestate cache does not contain information for the received encodedmessage, then displaying a temporary message indicator to the mobiledevice's user.
 16. The method of claim 15, further comprising the stepsof: performing full processing on the received encoded message;providing an indicator to the mobile device's user based upon the fullyprocessed encoded message.
 17. The method of claim 1, further comprisingthe steps of: determining that a message state change has occurred sincethe encoded message was last opened and the message state data wascached; providing an updated indicator to the mobile device's user thatreflects the message state change.
 18. The method of claim 17, wherein achange in the message state results from revocation of a digitalcertificate whose corresponding private key was used to sign an encodedmessage provided to the mobile device.
 19. The method of claim 17,wherein a change in the message state results from addition of a relateddigital certificate to a set of trusted certificates provided to themobile device.
 20. The method of claim 17, wherein the encoded messageis processed on a background thread running on the mobile device,wherein the background thread determines that a message state change hasoccurred and facilitates the providing of the updated indicator to themobile device's user.
 21. The method of claim 20, wherein the mobiledevice's user is only made visually aware of any background messageprocessing related to the encoded message when the generated messageindicator becomes incorrect due to a change in message state.
 22. Themethod of claim 1, wherein the cache is cleared of information about theencoded message based upon occurrence of a pre-selected event.
 23. Themethod of claim 22, wherein the event includes the mobile deviceentering into a locked mode or into a mode where the device is locked upand no activity can be performed by the user or wherein the user selectsa predetermined menu item on the mobile device.
 24. The method of claim1, wherein means for providing a wireless network and means forproviding an electronic mail message server are used to communicate theencoded message to the mobile device.
 25. The method of claim 1, whereinthe mobile device is a handheld wireless mobile communications device.26. A data signal that is transmitted using a communication channel,wherein the data signal includes the encoded message of claim 1; whereinthe communication channel is a network, wherein the data signal ispacketized data that is transmitted through a carrier wave across thenetwork.
 27. Computer-readable medium capable of causing a mobile deviceto perform the method of claim
 1. 28. The method of claim 1, wherein thefirst access of the encoded message is a user-initiated access of theencoded message.
 29. The method of claim 1, wherein the first access ofthe encoded message results from the mobile device accessing the encodedmessage upon receipt of the encoded message.
 30. The method of claim 1,wherein the message was closed between the first and second accesses ofthe encoded message.
 31. The method of claim 30, wherein pre-processingof the encoded message determines first message state data for storagein the cache; wherein the first message state data is retrieved from thecache in order to be displayed to the mobile device's user; whereinadditional message processing occurs after the first message state datais stored in the cache; wherein the additional message processingincludes decrypting the encoded message; wherein the additional messageprocessing provides second message state data that is used to update thedisplay of message state data to the user.
 32. The method of claim 1,wherein the generated message state data includes a security trust levelfor the encoded message.
 33. The method of claim 32, further comprisingthe steps of: accessing security-related data associated with theencoded message; accessing security-related trust categories that arestored on the mobile device; determining, based upon the accessedsecurity-related data, which of the security-related trust categoriescorresponds to the encoded message; storing the determinedsecurity-related trust category in the cache of the mobile device;accessing from the cache the stored security-related trust categorybased upon a second access of the encoded message, wherein the secondaccess occurs after the encoded message had been closed by the user;generating a security-related message indicator based upon thesecurity-related trust category that was accessed from the cache;wherein the security-related message indicator is provided to a user ofthe mobile device.
 34. The method of claim 33, wherein thesecurity-related message indicator is an indication of trust relative toencryption applied to the encoded message.
 35. The method of claim 33,wherein the security-related message indicator is an indication of trustrelative to digital signature used for the encoded message.
 36. Themethod of claim 33, wherein the security-related data indicates whichtype of security cipher algorithm was used with respect to the encodedmessage.
 37. An apparatus for handling an encoded message that wasreceived by a wireless mobile communications device, wherein state dataabout the encoded message is generated based upon a first opening of theencoded message, comprising: a message processor that stores thegenerated message state data in a cache of the mobile device; anaccessing module that, based upon a second opening of the encodedmessage, retrieves from the cache the stored message state data; whereina message indicator is generated based upon the message state data thatis accessed from the cache; wherein the generated message indicator isprovided to a user of the mobile device.
 38. A mobile device thathandles an encoded message comprising: means for receiving the encodedmessage over a wireless network; means for generating state data aboutthe encoded message; means for storing the message state data in acache; means for accessing from the cache the message state data whencontent of the received encoded message is to be retrieved; wherein themessage state data that was stored in the cache due to a first openingof the encoded message is available for retrieval from the cache for asecond opening of the encoded message; means for generating a messageindicator based upon the message state data that was accessed from thecache; wherein the generated message indicator is provided to a user ofthe mobile device.
 39. The mobile device of claim 38, wherein themessage state data that was stored in the cache due to a first openingof the encoded message is available for retrieval from the cache for athird opening of the encoded message.